home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TD on CD Volume 4 #2
/
TD on CD (Volume 4, Issue 2) (USA).bin
/
APPS
/
Citrix
/
READCUST.TXT
< prev
next >
Wrap
Text File
|
1996-09-06
|
8KB
|
194 lines
CUSTOMIZING THE WINFRAME TEST DRIVE DISKETTES
This document discusses how to customize the WinFrame Test Drive diskettes
with your company's logo and WinFrame server connection information.
Once you have created a set of customized Test Drive diskettes, you can
distribute them to your customers to demonstrate the benefits of Citrix
WinFrame and remote computing. Your customers install the Test Drive on
a PC and use it to connect to your WinFrame server over Dial-In and/or
TCP/IP connections and remotely run Windows applications you set up. See
the document "Planning Your WinFrame Test Drive System Installation" for
information on how to set up your WinFrame server.
The default settings in the Test Drive kit will connect your customers
to Citrix's WinFrame Test Drive server; however, we strongly recommend
that you implement your own WinFrame Test Drive Server. Having your
own Test Drive server system will:
1. Build your identity with your customers.
2. Give you total control over content.
3. Allow you to directly monitor the server activity, thus gaining
knowledge about your customers and prospects.
4. Give you the ability to provide customized on-site demonstrations.
Your not-for-resale WinFrame unit is the perfect solution for this system.
CONTENTS
The WinFrame Test Drive Customization Kit includes the following items:
* This document (READCUST.TXT), "Customizing the WinFrame Test
Drive Diskettes"
* The document "Planning Your WinFrame Test Drive System Installation"
* The WinFrame Win16 Test Drive Client diskette for Windows 3.1
and Windows for Workgroups
* The WinFrame Win32 Test Drive Client diskette for Windows 95
and Windows NT
HOW TO CUSTOMIZE YOUR WINFRAME TEST DRIVE DISKETTES
NOTE: Be sure to make backup copies of the WinFrame Test Drive diskettes
before modifying any files on the diskettes, in case you inadvertently
damage a file.
The Win16 and Win32 Test Drive diskettes contain the following files that
can be customized for your Test Drive configuration:
1. The initial bitmap splash screen, SETUP.BMP. This is a bitmap file that
is displayed when the Test Drive install program starts. You can use
this bitmap as-is, modify the bitmap with your logo and company
information, or delete this file to save space, in which case no initial
splash screen is displayed.
2. The Test Drive setup file, SETUP.INI. SETUP.INI is a standard format
Windows .INI file with sections and keys. The important sections and
keys include:
* The [Startup] section. This contains the name of the WinFrame Test
Drive application (AppName key). This is the name displayed on the
Test Drive setup screens. The default value is "WinFrame Test Drive".
For example, to change the name of the Test Drive application to
"Progressive Computing Test Drive", change the "AppName" line in
SETUP.INI to:
AppName = Progressive Computing Test Drive
This section also allows you to display the "AppName" in a smaller or
larger font size. The AppNameFontSize key can be changed based on
your "AppName" and the visual effect desired. The value set here is
checked against some reasonable limit, e.g. greater than zero;
however, the individual client PC can map this to an available size.
For example, to change the font size to 36 point type, change the
"AppNameFontSize" line in SETUP.INI to:
AppNameFontSize = 36
* The [WFTDrvCustConnTypes] section. This contains the connection
types supported (IP= and DIAL=). The lines:
IP = YES
DIAL = YES
are used to enable TCP/IP and Dial-Up support. If your WinFrame
server only supports one connection type, specify NO for the unused
connection type; for example, to enable Dial-In support only, specify:
IP = NO
DIAL = YES
* The [WFTDrvCustBitmaps] section. This contains the number and names
of any custom bitmap files that you supply (Count = n and Bitmapx =
bitmapfilename). See the section "Adding Custom Bitmaps" below for
more information on adding custom bitmaps.
3. The Test Drive connections file, TDAPPSRV.INI. TDAPPSRV.INI contains:
* The telephone number (PhoneNumber) of the WinFrame Test Drive server
for Dial-In connections. The default value is the telephone number of
the Citrix WinFrame Test Drive server.
* The TCP/IP address (Address) of the WinFrame Test Drive server for
TCP/IP connections. The default value is the TCP/IP address of the
Citrix WinFrame Test Drive server. This address can be entered as
a DNS name or as an IP address (for example, 204.32.22.9). Use the
DNS name if possible, since changing the IP address will render all
of your TCP/IP Test Drive installations inoperable.
4. This file, READCUST.TXT, which should be removed prior to release to
your customers. Removing this file also frees up approximately 8 KB
of additional diskette space for bitmaps.
ADDING CUSTOM BITMAPS
You can supply your own custom bitmaps on the Test Drive diskette. These
bitmaps should be 16-color and no larger than 440x275 pixels (WxH). The
[WFTDrvCustBitmaps] section in SETUP.INI uses the key values Count=n and
Bitmapx=bitmapfilename, where n is the total number of custom bitmaps and
x is the number of a bitmap file, to specify the optional bitmaps. The
bitmaps are displayed at the beginning of the installation process after
the initial splash screen in the order set by the Bitmapx statements, and
the user can scroll through the bitmaps using the Next and Back buttons.
For example, to display three bitmaps named COMPINFO.BMP, WFINFO.BMP, and
ORDERNFO.BMP, you would place the following lines in your SETUP.INI file:
[WFTDrvCustBitmaps]
Count = 3
Bitmap1 = COMPINFO.BMP
Bitmap2 = WFINFO.BMP
Bitmap3 = ORDERNFO.BMP
If you do not use any optional bitmaps, the default "Welcome" panel is
automatically used. Because the optional bitmaps can have widely differing
space requirements and there is not much free space on a single 1.44 MB
diskette, bitmaps can be optionally compressed. The optional bitmaps may be
placed on the diskette in one of three forms:
1. Uncompressed bitmap files placed on the installation diskette, with
the bitmap file names specified as shown above.
2. Bitmap files contained in a Windows, self-extracting executable file.
In this case, only the Windows-based executable, which must be named
CUSTBMPS.EXE, is needed, and you must remove the CUSTBMPS.PIF file.
The Windows-based executable can do numerous things; however, after
it terminates the files for the corresponding bitmaps must be present
in the temporary support directory (the current directory when
CUSTBMPS.EXE is executed).
3. Bitmap files contained in a non-Windows, self-extracting executable
file, using a package such as PKZIP (not supplied). For example,
PKZIP can be used to compress the bitmaps into a .ZIP file, which is
then converted to a self-extracting executable named CUSTBMPS.EXE.
In this case, both the self-extracting executable and a Windows
Program Information (PIF) file, which must be named CUSTBMPS.PIF,
need to be on the installation diskette, and the PIF file must run
the self-extracting .EXE file. A sample CUSTBMPS.PIF is supplied on
the Test Drive diskettes as CUSTBMPS.SMP. If you are using the
CUSTBMPS.EXE method described above, insure this in NOT named to its
active form (CUSTBMPS.PIF).
A SAMPLE SETUP.INI FILE
Here is a sample SETUP.INI file with the following features:
* The name displayed on the setup screens is
"Progressive Computing Test Drive"
* Three bitmaps, named COMPINFO.BMP, WFINFO.BMP,
and ORDERNFO.BMP are displayed
* Only Dial-In connections are supported
[Startup]
AppName = Progressive Computing Test Drive
[WFTDrvCustConnTypes]
IP = NO
DIAL = YES
[WFTDrvCustBitmaps]
Count = 3
Bitmap1 = compinfo.bmp
Bitmap2 = wfinfo.bmp
Bitmap3 = ordernfo.bmp